fix(site): derive Updated date from registry data#13
Merged
garysheng merged 1 commit intoPeonPing:mainfrom Mar 11, 2026
Merged
Conversation
… time The /packs page was showing the ISR render timestamp via new Date(), which was misleading. Now computes max(dateUpdated) across all packs and passes it as a prop to the client component.
|
@taylan is attempting to deploy a commit to the Gary Sheng's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
new Date()at render time, showing the ISR cache timestamp instead of when pack data actually changedmax(dateUpdated)across all registry packs server-side and passes it as a propTest plan
npm run buildpassesupdatedfield in the registry